perm filename X3J13.MSG[COM,LSP]1 blob
sn#834001 filedate 1987-02-09 generic text, type C, neo UTF8
COMMENT ⊗ VALID 00001 PAGES
C REC PAGE DESCRIPTION
C00001 00001
C00002 ENDMK
C⊗;
∂06-Feb-87 2207 RPG next x3j13 agenda
∂06-Feb-87 1753 FAHLMAN@C.CS.CMU.EDU next x3j13 agenda
Received: from C.CS.CMU.EDU by SAIL.STANFORD.EDU with TCP; 6 Feb 87 17:49:10 PST
Received: ID <FAHLMAN@C.CS.CMU.EDU>; Fri 6 Feb 87 20:48:38-EST
Date: Fri, 6 Feb 1987 20:48 EST
Message-ID: <FAHLMAN.12277009706.BABYL@C.CS.CMU.EDU>
Sender: FAHLMAN@C.CS.CMU.EDU
From: "Scott E. Fahlman" <Fahlman@C.CS.CMU.EDU>
To: MATHIS@ADA20.ISI.EDU
Cc: bobrow.pa@XEROX.COM, gls@ZARATHUSTRA.THINK.COM, rpg@SAIL.STANFORD.EDU,
scherlis@VAX.DARPA.MIL, squires@VAX.DARPA.MIL,
willc%tekchips@RELAY.CS.NET
Subject: next x3j13 agenda
In-reply-to: Msg of 3 Feb 1987 17:34-EST from MATHIS at ADA20.ISI.EDU
That leaves Wed morning for the "cleanup" committee. That may be
right for an initial session of that type, but we cann't expect
much in the way of results.
The compiler committee may actually have more to present than the
cleanup committee. Rob Maclachlan has produced an excellent proposal
that looks to me like it might fix up almost all the outstanding
compilation issues at one swoop. Whether the rest of the compiler
committee will want to put this forward as a proposal, I can't say.
Unfortunately, Rob won't be at this meeting (CMU has no budget for such
travel), but perhaps one of the other compiler committee people will
want to present Rob's proposal.
I think that the cleanup committee is going to have to be reorganized so
that some work gets done. Most of the original members have been
inactive, and some have been downright incommunicado. I think we're
going to have to oust the inactive members and try to add some new ones
with more time and energy for this task. I think this will need to be
discussed by mail BEFORE the meeting, rather than trying to solve the
problem in the middle of the conference. If we just ask for volunteers,
we'll get all the wrong people and things will be even worse than now.
I think that the right move might be to invite some specific people to
join the committee and help out: Rob, Skef Wholey, Eric Benson...people
who might be able to grab a few issues and run with them.
I don't know if there will be anything to report on errors, presentation
of the standard, windows, or the other issues that had committees set up
for them.
Any chance that a more or less final object proposal will be ready for
circulation before the meeting?
I don't see any point in wasting any more time on Lisp1/Lisp2 until
someone has a coherent Macro proposal to present and some better ideas
on how to automate the transition. No sense plowing the same technical
ground and stating the same opinions over and over again, unless the
plan is to bring this to a final vote and be done with it once and for
all.
-- Scott
∂09-Feb-87 1033 RPG Re: next x3j13 agenda
∂09-Feb-87 0851 Bobrow.pa@Xerox.COM Re: next x3j13 agenda
Received: from XEROX.COM by SAIL.STANFORD.EDU with TCP; 9 Feb 87 08:51:12 PST
Received: from Cabernet.ms by ArpaGateway.ms ; 09 FEB 87 08:44:44 PST
Date: 9 Feb 87 08:44 PST
Sender: Bobrow.pa@Xerox.COM
From: Danny Bobrow <Bobrow.pa@Xerox.COM>
Subject: Re: next x3j13 agenda
In-reply-to: "Scott E. Fahlman" <Fahlman@C.CS.CMU.EDU>'s message of Fri,
6 Feb 87 20:48 EST
To: Fahlman@C.CS.CMU.EDU
cc: MATHIS@ADA20.ISI.EDU, bobrow.pa@Xerox.COM,
gls@ZARATHUSTRA.THINK.COM, rpg@SAIL.STANFORD.EDU,
scherlis@VAX.DARPA.MIL, squires@VAX.DARPA.MIL,
willc%tekchips@RELAY.CS.NET
Message-ID: <870209-084444-5562@Xerox>
Any chance that a more or less final object proposal will be
ready for circulation before the meeting?
We expect to circualte a document to the committee so that it can be
presented. As to what "final" means, we have mostly agreed on most of
the contents, but what happens when the committee sees it.
danny